Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 047fe4bb2ba07862754e701a9da65be91f368d8f6a05f934cdd46bbf906756fc

Tx prefix hash: 77deb967afadcab12a78e4c68900e0c1bd79b98a819fe9d4d0aaf893471fdda6
Tx public key: c25f2db8d63f831ee081db0d7da179854597a4fbb643bdf6f18f903a74d4b266
Timestamp: 1738190020 Timestamp [UCT]: 2025-01-29 22:33:40 Age [y:d:h:m:s]: 00:336:23:33:24
Block: 1207939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238662 RingCT/type: yes/0
Extra: 01c25f2db8d63f831ee081db0d7da179854597a4fbb643bdf6f18f903a74d4b266021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf37dfc9547b4a1d5afab17f18dac0e5ded88585fac2531d052ebb385c942fc3 0.600000000000 1694666 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": 1207949, "vin": [ { "gen": { "height": 1207939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf37dfc9547b4a1d5afab17f18dac0e5ded88585fac2531d052ebb385c942fc3" } } ], "extra": [ 1, 194, 95, 45, 184, 214, 63, 131, 30, 224, 129, 219, 13, 125, 161, 121, 133, 69, 151, 164, 251, 182, 67, 189, 246, 241, 143, 144, 58, 116, 212, 178, 102, 2, 17, 0, 0, 0, 1, 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