Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 90bfd041ba9691cb0a8f1fd2009a39ae0ed8b48f22d7898b692547968cffc9c3

Tx prefix hash: e8da80c2da63fa07e95e41c47166342d6990b931041c03b0e3b7a7900599d94f
Tx public key: ce65b2e8f3881591bd42d5a4838cc7f9730fbe609c6e9e590d9be874a2af4cce
Timestamp: 1706585120 Timestamp [UCT]: 2024-01-30 03:25:20 Age [y:d:h:m:s]: 01:252:19:19:39
Block: 946315 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439434 RingCT/type: yes/0
Extra: 01ce65b2e8f3881591bd42d5a4838cc7f9730fbe609c6e9e590d9be874a2af4cce02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d827446433dc0570cfbb85ea607cdff4ad7c7670d28e571e8501c7a5f893f70b 0.600000000000 1404647 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 946325, "vin": [ { "gen": { "height": 946315 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d827446433dc0570cfbb85ea607cdff4ad7c7670d28e571e8501c7a5f893f70b" } } ], "extra": [ 1, 206, 101, 178, 232, 243, 136, 21, 145, 189, 66, 213, 164, 131, 140, 199, 249, 115, 15, 190, 96, 156, 110, 158, 89, 13, 155, 232, 116, 162, 175, 76, 206, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8