Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 352e7a54d88f544303967e0e5a94ed7fcd6fc88bceb67fb399aba3ec44c59679

Tx prefix hash: c0fd9d94e8cff74ee02be6ba83d1866eeada428836f5fa0a46c74de052cf1ab9
Tx public key: 4d9aa730a8946e556ce5f92fa5f525d59cf6e44382371229db32b2effa5baa2d
Timestamp: 1704312910 Timestamp [UCT]: 2024-01-03 20:15:10 Age [y:d:h:m:s]: 00:329:23:54:57
Block: 927516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236260 RingCT/type: yes/0
Extra: 014d9aa730a8946e556ce5f92fa5f525d59cf6e44382371229db32b2effa5baa2d02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5355617e6da2a7a6a4602c30f0267b2eb5a78a291193b59a8d6af047ebc02785 0.600000000000 1385352 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": 927526, "vin": [ { "gen": { "height": 927516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5355617e6da2a7a6a4602c30f0267b2eb5a78a291193b59a8d6af047ebc02785" } } ], "extra": [ 1, 77, 154, 167, 48, 168, 148, 110, 85, 108, 229, 249, 47, 165, 245, 37, 213, 156, 246, 228, 67, 130, 55, 18, 41, 219, 50, 178, 239, 250, 91, 170, 45, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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