Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc0725e0a762a7bb5566e64d801b3c0125f1666cb73a7c84f7bda81815ede782

Tx prefix hash: 9d6e778b618554045840260846b650af0e8541ced4ad0567dbc13409399873d8
Tx public key: b24030809e39d3ec5bbc9bce7fefec1b454c0e4a3954a63aa4d0468a23b2ea54
Timestamp: 1729207724 Timestamp [UCT]: 2024-10-17 23:28:44 Age [y:d:h:m:s]: 00:096:18:45:16
Block: 1133893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69130 RingCT/type: yes/0
Extra: 01b24030809e39d3ec5bbc9bce7fefec1b454c0e4a3954a63aa4d0468a23b2ea540211000000033cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f00dd90391862314226d54f52d7a81882413468926fc9eae9bfeeffbea08a19f 0.600000000000 1617108 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": 1133903, "vin": [ { "gen": { "height": 1133893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f00dd90391862314226d54f52d7a81882413468926fc9eae9bfeeffbea08a19f" } } ], "extra": [ 1, 178, 64, 48, 128, 158, 57, 211, 236, 91, 188, 155, 206, 127, 239, 236, 27, 69, 76, 14, 74, 57, 84, 166, 58, 164, 208, 70, 138, 35, 178, 234, 84, 2, 17, 0, 0, 0, 3, 60, 208, 252, 6, 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