Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23621f106892c6bf4c0eb9649852fc7fdf9b9e81cc0ccbd9099dd0432cb38abc

Tx prefix hash: ae7cd613b2c039229b5452ace4590a6ad3e410ec4c3d9d26c50aeb85ec70cc6f
Tx public key: e892e70e51aa4388d1502e4cba92e36a7e3c6a3b506695e13d2aa8c62b99365a
Timestamp: 1707919910 Timestamp [UCT]: 2024-02-14 14:11:50 Age [y:d:h:m:s]: 01:094:08:07:50
Block: 957393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328494 RingCT/type: yes/0
Extra: 01e892e70e51aa4388d1502e4cba92e36a7e3c6a3b506695e13d2aa8c62b99365a0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50814926289d9dd8f2e979bc277dcbbc1462809f729cc880b019c3e90163f7f9 0.600000000000 1416711 of 15

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": 957403, "vin": [ { "gen": { "height": 957393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50814926289d9dd8f2e979bc277dcbbc1462809f729cc880b019c3e90163f7f9" } } ], "extra": [ 1, 232, 146, 231, 14, 81, 170, 67, 136, 209, 80, 46, 76, 186, 146, 227, 106, 126, 60, 106, 59, 80, 102, 149, 225, 61, 42, 168, 198, 43, 153, 54, 90, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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