Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db9c9923d462dc6ef8cff018e98a716ba4c7b6010bc11ba7684f3807a90be6f9

Tx prefix hash: d2a37acd09b0d03d5192e5027e8f3e3c738192fcf47f7fe2de217570e4e91429
Tx public key: 6280a638b9c35fcf6995f2f1d856a14e34fd7fa7bcf299603d04a7906f4cb219
Timestamp: 1736657830 Timestamp [UCT]: 2025-01-12 04:57:10 Age [y:d:h:m:s]: 00:158:03:36:59
Block: 1195511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112725 RingCT/type: yes/0
Extra: 016280a638b9c35fcf6995f2f1d856a14e34fd7fa7bcf299603d04a7906f4cb2190211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df1f22f96f2fd68e46da29da8b5b825774abc0491558bd8ea8d12f071134a8e4 0.600000000000 1682102 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": 1195521, "vin": [ { "gen": { "height": 1195511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df1f22f96f2fd68e46da29da8b5b825774abc0491558bd8ea8d12f071134a8e4" } } ], "extra": [ 1, 98, 128, 166, 56, 185, 195, 95, 207, 105, 149, 242, 241, 216, 86, 161, 78, 52, 253, 127, 167, 188, 242, 153, 96, 61, 4, 167, 144, 111, 76, 178, 25, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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