Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7215cf2bc3cb5fc2c89c8a90d134cb3e44fd8d807da73a5c64b4baea4f3da0c7

Tx prefix hash: c6a6ede6cf0db3cd95425c98b36f15962ab843094a44156748f33bac96644419
Tx public key: 5bc94211f81988fa0fe079a1c0c86b57b182078ac0b75455fab53cd4a373184b
Timestamp: 1648257740 Timestamp [UCT]: 2022-03-26 01:22:20 Age [y:d:h:m:s]: 03:220:21:56:24
Block: 466467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 935784 RingCT/type: yes/0
Extra: 015bc94211f81988fa0fe079a1c0c86b57b182078ac0b75455fab53cd4a373184b0211000000054a0f5013000000000000000000

1 output(s) for total of 17.474366653000 dcy

stealth address amount amount idx
00: 3ecf75510fdcdd797d4c09b4778a3f20af10680c16289ef2347817f4243ccc9e 17.474366653000 884788 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": 466477, "vin": [ { "gen": { "height": 466467 } } ], "vout": [ { "amount": 17474366653, "target": { "key": "3ecf75510fdcdd797d4c09b4778a3f20af10680c16289ef2347817f4243ccc9e" } } ], "extra": [ 1, 91, 201, 66, 17, 248, 25, 136, 250, 15, 224, 121, 161, 192, 200, 107, 87, 177, 130, 7, 138, 192, 183, 84, 85, 250, 181, 60, 212, 163, 115, 24, 75, 2, 17, 0, 0, 0, 5, 74, 15, 80, 19, 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