Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44f68507e5e6c18368fa2e48fc37f84c779a8e606f7c61c80236b4a7591657cf

Tx prefix hash: 8e0aea011bc5dcc36f61099ae3f02de9363b0126d4fb1df77e75a631e4624b4b
Tx public key: 719338d054baa48405b98d4769bf1b81d336d6f59d216c29f9ce7a910e7d0e8e
Timestamp: 1725237658 Timestamp [UCT]: 2024-09-02 00:40:58 Age [y:d:h:m:s]: 00:241:05:40:43
Block: 1100985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172257 RingCT/type: yes/0
Extra: 01719338d054baa48405b98d4769bf1b81d336d6f59d216c29f9ce7a910e7d0e8e021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecebcb05b251c55255ef7d133da93b6b224e1c4b45eabd0102e2057c2ff29df6 0.600000000000 1576966 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": 1100995, "vin": [ { "gen": { "height": 1100985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecebcb05b251c55255ef7d133da93b6b224e1c4b45eabd0102e2057c2ff29df6" } } ], "extra": [ 1, 113, 147, 56, 208, 84, 186, 164, 132, 5, 185, 141, 71, 105, 191, 27, 129, 211, 54, 214, 245, 157, 33, 108, 41, 249, 206, 122, 145, 14, 125, 14, 142, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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