Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 313eafd8f2fac731126af767aede6a26ffac49eaa914695cb8aac86d0e6a971f

Tx prefix hash: a34dda3297d448233ccf5eca6e89d584b2f728d62e575e9322992b1e3e3b8c7d
Tx public key: 7d3b92e9ec2823d4a0e464e19506981838f5db130467794ec943f67b86015374
Timestamp: 1745950257 Timestamp [UCT]: 2025-04-29 18:10:57 Age [y:d:h:m:s]: 00:248:16:11:08
Block: 1272184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175508 RingCT/type: yes/0
Extra: 017d3b92e9ec2823d4a0e464e19506981838f5db130467794ec943f67b8601537402110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ae89e4b74a2c19ab438184a9dc821c284723b29ab7f0af51adaf4b4258276e2 0.600000000000 1759457 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": 1272194, "vin": [ { "gen": { "height": 1272184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ae89e4b74a2c19ab438184a9dc821c284723b29ab7f0af51adaf4b4258276e2" } } ], "extra": [ 1, 125, 59, 146, 233, 236, 40, 35, 212, 160, 228, 100, 225, 149, 6, 152, 24, 56, 245, 219, 19, 4, 103, 121, 78, 201, 67, 246, 123, 134, 1, 83, 116, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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