Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 180032c8d1424023c38393416fce17d940c4289dc10d9e5d38a5221f5106b3e1

Tx prefix hash: 7343ceb681cb96803f9cae40149dc7d34610e26dfce9577e46ba4f187d8c778b
Tx public key: 6e19cee2374580aff2bbd9572aeba3ca17fbee6376f4359f2bc7c8fe55d2e372
Timestamp: 1699070776 Timestamp [UCT]: 2023-11-04 04:06:16 Age [y:d:h:m:s]: 01:226:17:13:41
Block: 884250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422948 RingCT/type: yes/0
Extra: 016e19cee2374580aff2bbd9572aeba3ca17fbee6376f4359f2bc7c8fe55d2e37202110000000733af99f4000000000000000000

1 output(s) for total of 0.721294610000 dcy

stealth address amount amount idx
00: 256543de64f7abb40ed02d4ed5302b19a69847b2ba5644a1d7380da3e7e36fa0 0.721294610000 1339987 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": 884260, "vin": [ { "gen": { "height": 884250 } } ], "vout": [ { "amount": 721294610, "target": { "key": "256543de64f7abb40ed02d4ed5302b19a69847b2ba5644a1d7380da3e7e36fa0" } } ], "extra": [ 1, 110, 25, 206, 226, 55, 69, 128, 175, 242, 187, 217, 87, 42, 235, 163, 202, 23, 251, 238, 99, 118, 244, 53, 159, 43, 199, 200, 254, 85, 210, 227, 114, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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