Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70ceee6f37d7de9399cefa40905db77624cd5c35b3aceb8be1e3bc3bb419bf86

Tx prefix hash: 8dc216dcdad83c308016734ba828733153d9712052e54de7da13c4e51a02f98c
Tx public key: 1e95c4b687c7aa2b49655353e5294e1c0570dc9fc5b2d5d00e1b34d5c29f15d1
Timestamp: 1674856770 Timestamp [UCT]: 2023-01-27 21:59:30 Age [y:d:h:m:s]: 02:117:19:00:04
Block: 684179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 605856 RingCT/type: yes/0
Extra: 011e95c4b687c7aa2b49655353e5294e1c0570dc9fc5b2d5d00e1b34d5c29f15d10211000000017e406890000000000000000000

1 output(s) for total of 3.319180675000 dcy

stealth address amount amount idx
00: de1fab2dec228c1efeba6e7281d6809b741a2f4c9ca2a1f075a5e7ce1b0cd822 3.319180675000 1126392 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": 684189, "vin": [ { "gen": { "height": 684179 } } ], "vout": [ { "amount": 3319180675, "target": { "key": "de1fab2dec228c1efeba6e7281d6809b741a2f4c9ca2a1f075a5e7ce1b0cd822" } } ], "extra": [ 1, 30, 149, 196, 182, 135, 199, 170, 43, 73, 101, 83, 83, 229, 41, 78, 28, 5, 112, 220, 159, 197, 178, 213, 208, 14, 27, 52, 213, 194, 159, 21, 209, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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