Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa36effdf9d7f2dd2008e61dbce1db06400f854ffc53f8621d736a7dc5a3c1cf

Tx prefix hash: a383f36b28b6053588f60661959a90ac750e83ec41fe2bd78d4d7be4b3e08e42
Tx public key: 869f619bee2223eaa3be5d8a5624beaa8e5d5ff3cf77ad3870e7e67c35cc9bd0
Timestamp: 1728789312 Timestamp [UCT]: 2024-10-13 03:15:12 Age [y:d:h:m:s]: 00:152:12:02:00
Block: 1130424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108781 RingCT/type: yes/0
Extra: 01869f619bee2223eaa3be5d8a5624beaa8e5d5ff3cf77ad3870e7e67c35cc9bd002110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e1452b20b9432b339930249cdff183bd852edea6dd0fcd5405efcbc14142e15 0.600000000000 1613301 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": 1130434, "vin": [ { "gen": { "height": 1130424 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e1452b20b9432b339930249cdff183bd852edea6dd0fcd5405efcbc14142e15" } } ], "extra": [ 1, 134, 159, 97, 155, 238, 34, 35, 234, 163, 190, 93, 138, 86, 36, 190, 170, 142, 93, 95, 243, 207, 119, 173, 56, 112, 231, 230, 124, 53, 204, 155, 208, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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