Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 483049ee8ac557e9bf6c679fddf2741cbc7a937e215e9209bf4e7588906143d3

Tx prefix hash: e1fbe16efdcb8dfd0ec0b9afe25e4c16c0a62819befaef25097ed7a886021d98
Tx public key: 8be59324447b67b819ea7c719f7f05c05aebd65c49088922a80acda77bbdbd19
Timestamp: 1741704034 Timestamp [UCT]: 2025-03-11 14:40:34 Age [y:d:h:m:s]: 00:255:00:24:09
Block: 1237038 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179982 RingCT/type: yes/0
Extra: 018be59324447b67b819ea7c719f7f05c05aebd65c49088922a80acda77bbdbd19021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94dad24f1e612c901d384eee1ca01ca881c32941cddc65dadb5eb7b6c20d5be7 0.600000000000 1723993 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": 1237048, "vin": [ { "gen": { "height": 1237038 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94dad24f1e612c901d384eee1ca01ca881c32941cddc65dadb5eb7b6c20d5be7" } } ], "extra": [ 1, 139, 229, 147, 36, 68, 123, 103, 184, 25, 234, 124, 113, 159, 127, 5, 192, 90, 235, 214, 92, 73, 8, 137, 34, 168, 10, 205, 167, 123, 189, 189, 25, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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