Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6c8e6d2181787e6be89967118832d7fb9500818144f4ff3f0bbdcc2bbec6b3f

Tx prefix hash: 827f502e699ac67fc2e403189576a8c4ad691c08803e0f15c0c6435cdbf6b6ab
Tx public key: 3ad6947b8d00db12caf72441ff5860500d67ca7d77f443f061f8799d2ff86d0e
Timestamp: 1723010210 Timestamp [UCT]: 2024-08-07 05:56:50 Age [y:d:h:m:s]: 00:261:13:59:26
Block: 1082507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186865 RingCT/type: yes/0
Extra: 013ad6947b8d00db12caf72441ff5860500d67ca7d77f443f061f8799d2ff86d0e02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79075948a5abc3cac9c41d13fe40bdd6032de0c8961d8f77cd9d21aa792de9df 0.600000000000 1556336 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": 1082517, "vin": [ { "gen": { "height": 1082507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79075948a5abc3cac9c41d13fe40bdd6032de0c8961d8f77cd9d21aa792de9df" } } ], "extra": [ 1, 58, 214, 148, 123, 141, 0, 219, 18, 202, 247, 36, 65, 255, 88, 96, 80, 13, 103, 202, 125, 119, 244, 67, 240, 97, 248, 121, 157, 47, 248, 109, 14, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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