Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 447b744783ae96ddf3866a9be7227c057b12ed26aeeb74dd114e8444fe2869b8

Tx prefix hash: 72eea9a3515c30fb4aa5c1aaa3f3adccf9ef7b8441f7d5da2309ce98b52281c5
Tx public key: fea41022496be76749242dab1c0c100b712f11e2a3efe8a477797080f8ed6d9a
Timestamp: 1714847492 Timestamp [UCT]: 2024-05-04 18:31:32 Age [y:d:h:m:s]: 00:252:23:50:31
Block: 1014849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181071 RingCT/type: yes/0
Extra: 01fea41022496be76749242dab1c0c100b712f11e2a3efe8a477797080f8ed6d9a02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67fc9cc819adeaeacd5d096af3cfb106f8a7f9c71299abfb1a7848dffed21342 0.600000000000 1478054 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": 1014859, "vin": [ { "gen": { "height": 1014849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67fc9cc819adeaeacd5d096af3cfb106f8a7f9c71299abfb1a7848dffed21342" } } ], "extra": [ 1, 254, 164, 16, 34, 73, 107, 231, 103, 73, 36, 45, 171, 28, 12, 16, 11, 113, 47, 17, 226, 163, 239, 232, 164, 119, 121, 112, 128, 248, 237, 109, 154, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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