Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1be2d55c213b986f76046f2b34ec5d2f011bd974f45584f8b945b0b08be5d14a

Tx prefix hash: 001f4215b508d1e1c4df910bf9df4fb443bd3b4550b99862fcae7d1db40834d4
Tx public key: d9cdcc0a62709bde10a4b3fac09b394f64c8d0bb4f722e39d28cbffa4912f770
Timestamp: 1576643287 Timestamp [UCT]: 2019-12-18 04:28:07 Age [y:d:h:m:s]: 05:021:18:14:49
Block: 28135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1163612 RingCT/type: yes/0
Extra: 01d9cdcc0a62709bde10a4b3fac09b394f64c8d0bb4f722e39d28cbffa4912f770021100000007ad433a0b000000000000000000

1 output(s) for total of 495.196915217000 dcy

stealth address amount amount idx
00: 483e24aef0dfa87c8ccf4ebaa438882fa3a8ea9845edadd9d2424760abf33ed6 495.196915217000 46663 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": 28145, "vin": [ { "gen": { "height": 28135 } } ], "vout": [ { "amount": 495196915217, "target": { "key": "483e24aef0dfa87c8ccf4ebaa438882fa3a8ea9845edadd9d2424760abf33ed6" } } ], "extra": [ 1, 217, 205, 204, 10, 98, 112, 155, 222, 16, 164, 179, 250, 192, 155, 57, 79, 100, 200, 208, 187, 79, 114, 46, 57, 210, 140, 191, 250, 73, 18, 247, 112, 2, 17, 0, 0, 0, 7, 173, 67, 58, 11, 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