Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e55ab9433cf2e279d26d74cb72fc54c2c3c97e03cb9ddc2a132e22a245bf9f7

Tx prefix hash: b8599c6e95240b23e033abedec85dc4b80a4da70f5b4d6a12f45848117238078
Tx public key: 8b0ac4979cdc7ea604debd361ff0069226f93248164a116ff5002ad6e1dc2c33
Timestamp: 1574750046 Timestamp [UCT]: 2019-11-26 06:34:06 Age [y:d:h:m:s]: 05:185:15:14:24
Block: 17700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1275338 RingCT/type: yes/0
Extra: 018b0ac4979cdc7ea604debd361ff0069226f93248164a116ff5002ad6e1dc2c3302110000001c5d286194000000000000000000

1 output(s) for total of 536.232870909000 dcy

stealth address amount amount idx
00: e715f83070500ba07b7276445c1ad1f2ba8fd7e9359c7768e2de0780c2bb1eef 536.232870909000 26114 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": 17710, "vin": [ { "gen": { "height": 17700 } } ], "vout": [ { "amount": 536232870909, "target": { "key": "e715f83070500ba07b7276445c1ad1f2ba8fd7e9359c7768e2de0780c2bb1eef" } } ], "extra": [ 1, 139, 10, 196, 151, 156, 220, 126, 166, 4, 222, 189, 54, 31, 240, 6, 146, 38, 249, 50, 72, 22, 74, 17, 111, 245, 0, 42, 214, 225, 220, 44, 51, 2, 17, 0, 0, 0, 28, 93, 40, 97, 148, 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