Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f059f873f127f012ff78e300be5620f59e7d2ba0f90b801bb3a7dff838900acb

Tx prefix hash: 4be3f33024e4146fccfb441fe02fb4edabe7c9ae571472fb3e976c5cf526cb0b
Tx public key: e3f5a64f791802cc0b6f1f56ff48e0aa92b1e4ef940e951c4d295eb95a817522
Timestamp: 1577142426 Timestamp [UCT]: 2019-12-23 23:07:06 Age [y:d:h:m:s]: 05:071:23:29:03
Block: 30171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1201360 RingCT/type: yes/0
Extra: 01e3f5a64f791802cc0b6f1f56ff48e0aa92b1e4ef940e951c4d295eb95a8175220211000000038a2ee0d9000000000000000000

1 output(s) for total of 487.564205552000 dcy

stealth address amount amount idx
00: 036e789dd8d6b26291ef07d0b4cb00c64a55adad99a694eda75eff972eb11f9a 487.564205552000 49819 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": 30181, "vin": [ { "gen": { "height": 30171 } } ], "vout": [ { "amount": 487564205552, "target": { "key": "036e789dd8d6b26291ef07d0b4cb00c64a55adad99a694eda75eff972eb11f9a" } } ], "extra": [ 1, 227, 245, 166, 79, 121, 24, 2, 204, 11, 111, 31, 86, 255, 72, 224, 170, 146, 177, 228, 239, 148, 14, 149, 28, 77, 41, 94, 185, 90, 129, 117, 34, 2, 17, 0, 0, 0, 3, 138, 46, 224, 217, 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