Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1613fcd4efdd9286f202ce4ab8a56b6fe07e13e3abec7f17dea7905a19ce71ee

Tx prefix hash: bd8d6e6e0495c1d19463dc37a8c923f9c67536c28ffb3d899464a949fffbfa5b
Tx public key: 750424a8afa49de40fc70e5b3da8e0fc9f20c7aeab2d7c968038a92d16c2bbd1
Timestamp: 1728403719 Timestamp [UCT]: 2024-10-08 16:08:39 Age [y:d:h:m:s]: 00:183:12:27:46
Block: 1127224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130954 RingCT/type: yes/0
Extra: 01750424a8afa49de40fc70e5b3da8e0fc9f20c7aeab2d7c968038a92d16c2bbd1021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b80433ee9ee9a2aa2f7a0f6237b438e95da413328ebaf4aefd5b9bac6aafbc3c 0.600000000000 1610025 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": 1127234, "vin": [ { "gen": { "height": 1127224 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b80433ee9ee9a2aa2f7a0f6237b438e95da413328ebaf4aefd5b9bac6aafbc3c" } } ], "extra": [ 1, 117, 4, 36, 168, 175, 164, 157, 228, 15, 199, 14, 91, 61, 168, 224, 252, 159, 32, 199, 174, 171, 45, 124, 150, 128, 56, 169, 45, 22, 194, 187, 209, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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