Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 649714463ee90d673f1ee8dd18f770e2013016f97869f0299b3da7188e04cde0

Tx prefix hash: 02ef70a7d7275e1af7b4f92295a60f880884a5d1b091b44fc197654e99d3169a
Tx public key: e71e5fc528233d579825e2c469a3bcfb94d3d712e70759b0fdc1a655fbed31a7
Timestamp: 1695505330 Timestamp [UCT]: 2023-09-23 21:42:10 Age [y:d:h:m:s]: 01:189:20:52:15
Block: 854679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396766 RingCT/type: yes/0
Extra: 01e71e5fc528233d579825e2c469a3bcfb94d3d712e70759b0fdc1a655fbed31a7021100000001faf35c9c000000000000000000

1 output(s) for total of 0.903844519000 dcy

stealth address amount amount idx
00: b313e042eb2a5b1186e013b29c300eab75781eb0d21de76341868f464b800331 0.903844519000 1308665 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": 854689, "vin": [ { "gen": { "height": 854679 } } ], "vout": [ { "amount": 903844519, "target": { "key": "b313e042eb2a5b1186e013b29c300eab75781eb0d21de76341868f464b800331" } } ], "extra": [ 1, 231, 30, 95, 197, 40, 35, 61, 87, 152, 37, 226, 196, 105, 163, 188, 251, 148, 211, 215, 18, 231, 7, 89, 176, 253, 193, 166, 85, 251, 237, 49, 167, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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