Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27ceb1f8b76bd278b14687d540948bfeaf9edb4efedfc2dd3f1c94b5a8c24cb1

Tx prefix hash: 4da28b8771bb14e2196e9b757b281f322596704453b68de606959cf14d6d6744
Tx public key: 77f46d1c15a623fb8781ce3134203941465055f3a505314505afe2277c1fbe7b
Timestamp: 1718423375 Timestamp [UCT]: 2024-06-15 03:49:35 Age [y:d:h:m:s]: 00:223:19:46:22
Block: 1044495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160115 RingCT/type: yes/0
Extra: 0177f46d1c15a623fb8781ce3134203941465055f3a505314505afe2277c1fbe7b021100000003cd63fb1b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31aebc19510a8f98b7b9559dc692d48d227e41d4514c0dac17e83a8b3e2dfae6 0.600000000000 1513818 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": 1044505, "vin": [ { "gen": { "height": 1044495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31aebc19510a8f98b7b9559dc692d48d227e41d4514c0dac17e83a8b3e2dfae6" } } ], "extra": [ 1, 119, 244, 109, 28, 21, 166, 35, 251, 135, 129, 206, 49, 52, 32, 57, 65, 70, 80, 85, 243, 165, 5, 49, 69, 5, 175, 226, 39, 124, 31, 190, 123, 2, 17, 0, 0, 0, 3, 205, 99, 251, 27, 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