Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aee6089900fea95ed56a29df8ff46e0c14e0c3e6e328b3378e87cd6eb7130d9c

Tx prefix hash: 57969728aa76a2bb007240c35821b1e650f58c18900e0ca7d05a6e4e7c24a272
Tx public key: 31cf328607fa46d43bf0efb656cfdbb0f5330609f857b9a1239844c1274ebfbf
Timestamp: 1699402027 Timestamp [UCT]: 2023-11-08 00:07:07 Age [y:d:h:m:s]: 01:150:05:46:51
Block: 886787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368573 RingCT/type: yes/0
Extra: 0131cf328607fa46d43bf0efb656cfdbb0f5330609f857b9a1239844c1274ebfbf021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.707467590000 dcy

stealth address amount amount idx
00: 2612795ca3b6e5d83dac1cf0c1d38380560a8f0343a09fe7b12ba797bc823bf5 0.707467590000 1342630 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": 886797, "vin": [ { "gen": { "height": 886787 } } ], "vout": [ { "amount": 707467590, "target": { "key": "2612795ca3b6e5d83dac1cf0c1d38380560a8f0343a09fe7b12ba797bc823bf5" } } ], "extra": [ 1, 49, 207, 50, 134, 7, 250, 70, 212, 59, 240, 239, 182, 86, 207, 219, 176, 245, 51, 6, 9, 248, 87, 185, 161, 35, 152, 68, 193, 39, 78, 191, 191, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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