Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d156b749f53fb0188f5af9eff097f889e634f2a85970fcc6b5d8f377da63f00a

Tx prefix hash: 409e54a348b3f2b234c2f32b0e950f8e3337ae5dc6400707a99e06c22dd3a491
Tx public key: 33e49f3f09f8799da6321c07c40973a563f8d6b429f90647cd71aece8f52157a
Timestamp: 1738275547 Timestamp [UCT]: 2025-01-30 22:19:07 Age [y:d:h:m:s]: 00:100:20:10:23
Block: 1208647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72124 RingCT/type: yes/0
Extra: 0133e49f3f09f8799da6321c07c40973a563f8d6b429f90647cd71aece8f52157a021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d89999e4799c5258d4b30d741fb400e35a7f7fbac0daa3385b655693e95293f5 0.600000000000 1695380 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": 1208657, "vin": [ { "gen": { "height": 1208647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d89999e4799c5258d4b30d741fb400e35a7f7fbac0daa3385b655693e95293f5" } } ], "extra": [ 1, 51, 228, 159, 63, 9, 248, 121, 157, 166, 50, 28, 7, 196, 9, 115, 165, 99, 248, 214, 180, 41, 249, 6, 71, 205, 113, 174, 206, 143, 82, 21, 122, 2, 17, 0, 0, 0, 7, 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