Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddc53fd8dc382ddd2b674f011ae8db83b4983dcbef403357966ceaa14fc4d274

Tx prefix hash: 50f9380b257f8856e6529f1101eee9ea63b0860553e2ee6b4121a51f1ca1aee3
Tx public key: 842f48109b78d7f0d1d77065a4bbd94e6ab8bbfa503a6b1f86a6c4e4a82e90f8
Timestamp: 1719611468 Timestamp [UCT]: 2024-06-28 21:51:08 Age [y:d:h:m:s]: 00:273:05:27:04
Block: 1054328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195229 RingCT/type: yes/0
Extra: 01842f48109b78d7f0d1d77065a4bbd94e6ab8bbfa503a6b1f86a6c4e4a82e90f80211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b41f9a5104bf843818f4810dcc41fca4d755e54cc3c00050b922d66773b4a4cc 0.600000000000 1524689 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": 1054338, "vin": [ { "gen": { "height": 1054328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b41f9a5104bf843818f4810dcc41fca4d755e54cc3c00050b922d66773b4a4cc" } } ], "extra": [ 1, 132, 47, 72, 16, 155, 120, 215, 240, 209, 215, 112, 101, 164, 187, 217, 78, 106, 184, 187, 250, 80, 58, 107, 31, 134, 166, 196, 228, 168, 46, 144, 248, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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