Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e17a5b50b09fa8dc2ab0f9acbb0c8e2cf52327517d76ab51b4777045bbaedb3b

Tx prefix hash: 163ad534ea0f53519d3aba30c4f74a8b3c77c41f8b3c101c0fba383f464a866b
Tx public key: 31bf04675a4abb40cb42573a6ad3cb5cb24144228d9c89b18e036fb2c9c2d1f5
Timestamp: 1721477576 Timestamp [UCT]: 2024-07-20 12:12:56 Age [y:d:h:m:s]: 00:272:16:42:06
Block: 1069804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194821 RingCT/type: yes/0
Extra: 0131bf04675a4abb40cb42573a6ad3cb5cb24144228d9c89b18e036fb2c9c2d1f5021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb86e4642cf47e85383506b9c1e4aec9444f6938144a6c4b0f8ba622fd04a502 0.600000000000 1541381 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": 1069814, "vin": [ { "gen": { "height": 1069804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb86e4642cf47e85383506b9c1e4aec9444f6938144a6c4b0f8ba622fd04a502" } } ], "extra": [ 1, 49, 191, 4, 103, 90, 74, 187, 64, 203, 66, 87, 58, 106, 211, 203, 92, 178, 65, 68, 34, 141, 156, 137, 177, 142, 3, 111, 178, 201, 194, 209, 245, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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