Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4444cf2c529e5ffeac3aab076c380b08b552713dabb902dc907647e3443fd179

Tx prefix hash: dac31759dec8ab2cf0a9ef953293b355e47b2d4542cce501f4b006a51c01e5b0
Tx public key: a54c26903cac18949f00664ed84926e2c940e7cd5d0e8dff57cc4e4b6cb4dac6
Timestamp: 1704346051 Timestamp [UCT]: 2024-01-04 05:27:31 Age [y:d:h:m:s]: 01:171:16:06:12
Block: 927784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383579 RingCT/type: yes/0
Extra: 01a54c26903cac18949f00664ed84926e2c940e7cd5d0e8dff57cc4e4b6cb4dac6021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30dff71cd4a8ed8ef8e22828bada340c135425a5eec024f7247fc770704ea324 0.600000000000 1385620 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": 927794, "vin": [ { "gen": { "height": 927784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30dff71cd4a8ed8ef8e22828bada340c135425a5eec024f7247fc770704ea324" } } ], "extra": [ 1, 165, 76, 38, 144, 60, 172, 24, 148, 159, 0, 102, 78, 216, 73, 38, 226, 201, 64, 231, 205, 93, 14, 141, 255, 87, 204, 78, 75, 108, 180, 218, 198, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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