Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36b6e1e69719db362d6074dbb91604a55c067c96ab1a2ae77d1b3a187cf6f39d

Tx prefix hash: dccc44499d30b5eeb940fdc49a13d8989d4e76271e1ee6e4de55ef6769d91739
Tx public key: bac2acafa98e773d1e31cf894fb9ad7c4dfe880e0b277e43a0dcb6847fbc9734
Timestamp: 1583750348 Timestamp [UCT]: 2020-03-09 10:39:08 Age [y:d:h:m:s]: 05:065:16:12:59
Block: 79069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1202662 RingCT/type: yes/0
Extra: 01bac2acafa98e773d1e31cf894fb9ad7c4dfe880e0b277e43a0dcb6847fbc97340211000000186d997e00000000000000000000

1 output(s) for total of 335.747178120000 dcy

stealth address amount amount idx
00: 047bcfcaa5ebd75261f88db50ead89bfabdb9c7c26803c32328d4cadf591e230 335.747178120000 144799 of 0

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": 79079, "vin": [ { "gen": { "height": 79069 } } ], "vout": [ { "amount": 335747178120, "target": { "key": "047bcfcaa5ebd75261f88db50ead89bfabdb9c7c26803c32328d4cadf591e230" } } ], "extra": [ 1, 186, 194, 172, 175, 169, 142, 119, 61, 30, 49, 207, 137, 79, 185, 173, 124, 77, 254, 136, 14, 11, 39, 126, 67, 160, 220, 182, 132, 127, 188, 151, 52, 2, 17, 0, 0, 0, 24, 109, 153, 126, 0, 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