Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed9084d6eae27ed544b826248f13362bad299b58f86de82f41faff09f9e07723

Tx prefix hash: 0c2f5ff5547388e236a421187b559f43a3db58e6c9bd14fb4b3dbcb0ba50af49
Tx public key: 33cdb7f4d2093c304e2f4ab2923dc091565c33ce3fda11cd5913e5041403f465
Timestamp: 1709578410 Timestamp [UCT]: 2024-03-04 18:53:30 Age [y:d:h:m:s]: 00:325:11:38:46
Block: 971159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232948 RingCT/type: yes/0
Extra: 0133cdb7f4d2093c304e2f4ab2923dc091565c33ce3fda11cd5913e5041403f46502110000000549a185bb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47370c1d829ac78c76c5325daaf3a4fca307ef3b1d3bd054d16f4d3ae0cb155a 0.600000000000 1431044 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": 971169, "vin": [ { "gen": { "height": 971159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47370c1d829ac78c76c5325daaf3a4fca307ef3b1d3bd054d16f4d3ae0cb155a" } } ], "extra": [ 1, 51, 205, 183, 244, 210, 9, 60, 48, 78, 47, 74, 178, 146, 61, 192, 145, 86, 92, 51, 206, 63, 218, 17, 205, 89, 19, 229, 4, 20, 3, 244, 101, 2, 17, 0, 0, 0, 5, 73, 161, 133, 187, 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