Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be08e9eaf58934513d3981b80c3ea8083abf3cd7cf8ec1e6ddb5e133a1fc9def

Tx prefix hash: b3f28e8cdc646a77fdc0d245983e3a0d7ae462fbe7fd1d08eb7d19281ce1c19b
Tx public key: 78217ce98f009c63666a624f8b818b72a49a532f8328e3b2fe26733641b0cfc9
Timestamp: 1629278596 Timestamp [UCT]: 2021-08-18 09:23:16 Age [y:d:h:m:s]: 03:170:13:38:02
Block: 316391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 895124 RingCT/type: yes/0
Extra: 0178217ce98f009c63666a624f8b818b72a49a532f8328e3b2fe26733641b0cfc902110000006f17696b73000000000000000000

1 output(s) for total of 54.911808001000 dcy

stealth address amount amount idx
00: c7dfaff008ddb06aa9f9fb8d7234b566c400322f2e8c2421f542ac13c609d6f4 54.911808001000 658230 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": 316401, "vin": [ { "gen": { "height": 316391 } } ], "vout": [ { "amount": 54911808001, "target": { "key": "c7dfaff008ddb06aa9f9fb8d7234b566c400322f2e8c2421f542ac13c609d6f4" } } ], "extra": [ 1, 120, 33, 124, 233, 143, 0, 156, 99, 102, 106, 98, 79, 139, 129, 139, 114, 164, 154, 83, 47, 131, 40, 227, 178, 254, 38, 115, 54, 65, 176, 207, 201, 2, 17, 0, 0, 0, 111, 23, 105, 107, 115, 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