Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c90edc575beecad94b0dfa67e78e1881d658591f2f3240e2445a9346f9ffaf38

Tx prefix hash: ded885d45bb73830f0754b35da378d0145d0fe25b5a3f30673eee2c2f3afcfff
Tx public key: f050a45be76c4168124bc785823a0921fc00c2f7a9d8e54e5b27ede1407c8fbb
Timestamp: 1737544746 Timestamp [UCT]: 2025-01-22 11:19:06 Age [y:d:h:m:s]: 00:147:13:18:37
Block: 1202813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105195 RingCT/type: yes/0
Extra: 01f050a45be76c4168124bc785823a0921fc00c2f7a9d8e54e5b27ede1407c8fbb021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a2cc75b6a9fdbd2b1a924e5e1fe4a19deb532c5431cd1af355c1e4fea961f0d 0.600000000000 1689480 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": 1202823, "vin": [ { "gen": { "height": 1202813 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a2cc75b6a9fdbd2b1a924e5e1fe4a19deb532c5431cd1af355c1e4fea961f0d" } } ], "extra": [ 1, 240, 80, 164, 91, 231, 108, 65, 104, 18, 75, 199, 133, 130, 58, 9, 33, 252, 0, 194, 247, 169, 216, 229, 78, 91, 39, 237, 225, 64, 124, 143, 187, 2, 17, 0, 0, 0, 8, 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