Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6eccced26fdb9e55a0e6b572d857d79de665e725864eeaeee3dfceeef50c6b4

Tx prefix hash: fb650d50e4ff4813d61530c86bfcd95eebd90db962ec98f01aa47dcbfbe4cf7d
Tx public key: fc780af62ff5d71a1ff3dc0421c60f0fe70171f46357660eff4d0c6caa9d99ea
Timestamp: 1730705610 Timestamp [UCT]: 2024-11-04 07:33:30 Age [y:d:h:m:s]: 00:146:21:41:37
Block: 1146222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104822 RingCT/type: yes/0
Extra: 01fc780af62ff5d71a1ff3dc0421c60f0fe70171f46357660eff4d0c6caa9d99ea0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 886fed19b556f1a2d98d93061a2a80ccdbcb3d7b5964f4187125e2501356b1cf 0.600000000000 1630817 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": 1146232, "vin": [ { "gen": { "height": 1146222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "886fed19b556f1a2d98d93061a2a80ccdbcb3d7b5964f4187125e2501356b1cf" } } ], "extra": [ 1, 252, 120, 10, 246, 47, 245, 215, 26, 31, 243, 220, 4, 33, 198, 15, 15, 231, 1, 113, 244, 99, 87, 102, 14, 255, 77, 12, 108, 170, 157, 153, 234, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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