Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cea1a9cfd1c61aa72892bc2a8ac5f5de7c6dc3a91936ce6007fd4d0db586cf4

Tx prefix hash: 02504e12a527886cf907e0b9de3b126eca0c11bdaed4019701afc7b232a5283c
Tx public key: 20448f0bbf2a51e9497adff2ca700f93b347399cb96b84a4e517bdeea66e6592
Timestamp: 1728783343 Timestamp [UCT]: 2024-10-13 01:35:43 Age [y:d:h:m:s]: 00:042:05:50:25
Block: 1130374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30161 RingCT/type: yes/0
Extra: 0120448f0bbf2a51e9497adff2ca700f93b347399cb96b84a4e517bdeea66e6592021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fddd2676760e70def9f9c5290c4a55665503de28a4a87765d0ff0732e307a23d 0.600000000000 1613249 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": 1130384, "vin": [ { "gen": { "height": 1130374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fddd2676760e70def9f9c5290c4a55665503de28a4a87765d0ff0732e307a23d" } } ], "extra": [ 1, 32, 68, 143, 11, 191, 42, 81, 233, 73, 122, 223, 242, 202, 112, 15, 147, 179, 71, 57, 156, 185, 107, 132, 164, 229, 23, 189, 238, 166, 110, 101, 146, 2, 17, 0, 0, 0, 4, 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