Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3a89ab6fc636fb2a2ed9cb410c9d06debbca5432c955abbe9e9264d0f277667

Tx prefix hash: bf02f8048d246933958c0a66480cb004e7ce483f3581e367d8e962ccc3abffa2
Tx public key: 49a79ccd499e004bcad0b4f81fb2b845bc55ccc5bd8146a01cbe70154136d6c3
Timestamp: 1686504681 Timestamp [UCT]: 2023-06-11 17:31:21 Age [y:d:h:m:s]: 01:212:14:17:16
Block: 780123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413332 RingCT/type: yes/0
Extra: 0149a79ccd499e004bcad0b4f81fb2b845bc55ccc5bd8146a01cbe70154136d6c302110000000433af99f4000000000000000000

1 output(s) for total of 1.596352569000 dcy

stealth address amount amount idx
00: 50844f3d480457c2a31a0fa05bad69db1ba18a8cb250acf3c86f6e6d3621d203 1.596352569000 1229820 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": 780133, "vin": [ { "gen": { "height": 780123 } } ], "vout": [ { "amount": 1596352569, "target": { "key": "50844f3d480457c2a31a0fa05bad69db1ba18a8cb250acf3c86f6e6d3621d203" } } ], "extra": [ 1, 73, 167, 156, 205, 73, 158, 0, 75, 202, 208, 180, 248, 31, 178, 184, 69, 188, 85, 204, 197, 189, 129, 70, 160, 28, 190, 112, 21, 65, 54, 214, 195, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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