Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ffcf6c71175ecdd632e6487873926cfbf33da2f271edce5ab6d04e73336de3c

Tx prefix hash: 37211a5dfe7d16ae238a45cd3950cb773e164013939c0a6288a6dd2f34a4f896
Tx public key: 387a3c1113c3f2ba2a1dc2b341eec98c6aec690ebca01f6895d613353c299c11
Timestamp: 1709708933 Timestamp [UCT]: 2024-03-06 07:08:53 Age [y:d:h:m:s]: 01:072:13:52:13
Block: 972249 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312884 RingCT/type: yes/0
Extra: 01387a3c1113c3f2ba2a1dc2b341eec98c6aec690ebca01f6895d613353c299c110211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f6e8ed872cc16df6fac91e0a25144f86427361ef8b6cbabbc44897450aa12f4 0.600000000000 1432158 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": 972259, "vin": [ { "gen": { "height": 972249 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f6e8ed872cc16df6fac91e0a25144f86427361ef8b6cbabbc44897450aa12f4" } } ], "extra": [ 1, 56, 122, 60, 17, 19, 195, 242, 186, 42, 29, 194, 179, 65, 238, 201, 140, 106, 236, 105, 14, 188, 160, 31, 104, 149, 214, 19, 53, 60, 41, 156, 17, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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