Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13fa906f3508a151ed3fea9e5e7c447a62255cdae0db58062f7e262f9efda52c

Tx prefix hash: de8e27e66cc4e25eeb4c735cbebfbc6524c1e118e2aefa492e377e54605425b0
Tx public key: bb95ce43af3e332395e063a40f8a6f3172667e78efed06b720a1df19f2ed7b06
Timestamp: 1682334647 Timestamp [UCT]: 2023-04-24 11:10:47 Age [y:d:h:m:s]: 02:048:07:44:02
Block: 745538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 556711 RingCT/type: yes/0
Extra: 01bb95ce43af3e332395e063a40f8a6f3172667e78efed06b720a1df19f2ed7b06021100000001e7ace25d000000000000000000

1 output(s) for total of 2.078422216000 dcy

stealth address amount amount idx
00: b6618fbef1905703adb5f5e78c7c27650175e297f0a0fa115aee470f1d37998f 2.078422216000 1192995 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": 745548, "vin": [ { "gen": { "height": 745538 } } ], "vout": [ { "amount": 2078422216, "target": { "key": "b6618fbef1905703adb5f5e78c7c27650175e297f0a0fa115aee470f1d37998f" } } ], "extra": [ 1, 187, 149, 206, 67, 175, 62, 51, 35, 149, 224, 99, 164, 15, 138, 111, 49, 114, 102, 126, 120, 239, 237, 6, 183, 32, 161, 223, 25, 242, 237, 123, 6, 2, 17, 0, 0, 0, 1, 231, 172, 226, 93, 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