Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c407d827e8859535beefa40ebeae1818b66841a1a770eda3bb1a252bdbdf6d5

Tx prefix hash: 3b71962fb21dd7e725d6c3e13ac1c250f9d68aee964ffc314af650d81066dac0
Tx public key: b4d5e4c9e54e6a26a1f57f2f10a8d7357d8d2d896d23726f7abe62032023c953
Timestamp: 1722090993 Timestamp [UCT]: 2024-07-27 14:36:33 Age [y:d:h:m:s]: 00:254:03:03:20
Block: 1074889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181524 RingCT/type: yes/0
Extra: 01b4d5e4c9e54e6a26a1f57f2f10a8d7357d8d2d896d23726f7abe62032023c953021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 210781baaaff6d3152d567d7a25d7bb85ad6caf2baf9ebf4470d5d490af36419 0.600000000000 1547408 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": 1074899, "vin": [ { "gen": { "height": 1074889 } } ], "vout": [ { "amount": 600000000, "target": { "key": "210781baaaff6d3152d567d7a25d7bb85ad6caf2baf9ebf4470d5d490af36419" } } ], "extra": [ 1, 180, 213, 228, 201, 229, 78, 106, 38, 161, 245, 127, 47, 16, 168, 215, 53, 125, 141, 45, 137, 109, 35, 114, 111, 122, 190, 98, 3, 32, 35, 201, 83, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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