Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94521292bb9e6a9226f9cbdd7b01d4cc887cd51987525d7d47b4ece2b4ed5f61

Tx prefix hash: f8064de4b7d2b986e4a160d7a2997141dc169a63ca3988a4fa8f4e2bb71d6d42
Tx public key: ec3fe92628837ede91961fcc73e9c4655a15bfc7645b1be348faecd0f7be8211
Timestamp: 1733582183 Timestamp [UCT]: 2024-12-07 14:36:23 Age [y:d:h:m:s]: 00:104:17:20:46
Block: 1170055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74640 RingCT/type: yes/0
Extra: 01ec3fe92628837ede91961fcc73e9c4655a15bfc7645b1be348faecd0f7be8211021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4028d24125f5ca4d52d9fb3a3878be5eca1b11c8f5e6c0733f591d2b33f988e 0.600000000000 1655784 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": 1170065, "vin": [ { "gen": { "height": 1170055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4028d24125f5ca4d52d9fb3a3878be5eca1b11c8f5e6c0733f591d2b33f988e" } } ], "extra": [ 1, 236, 63, 233, 38, 40, 131, 126, 222, 145, 150, 31, 204, 115, 233, 196, 101, 90, 21, 191, 199, 100, 91, 27, 227, 72, 250, 236, 208, 247, 190, 130, 17, 2, 17, 0, 0, 0, 4, 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