Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d7968f0611bc5247042398e64a0dbf77da7d7cab9f3d85f0f97ca090f8e5162

Tx prefix hash: 5470fba9b29ca978bff663f3ad01485fc02ee15c1ec3f0442393fc4c5b75439b
Tx public key: 52a9480fe9fe97e3f4a0d21e6741ac3cc654038d40a8177b7e04625c5fc87839
Timestamp: 1738427839 Timestamp [UCT]: 2025-02-01 16:37:19 Age [y:d:h:m:s]: 00:292:08:00:18
Block: 1209894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206693 RingCT/type: yes/0
Extra: 0152a9480fe9fe97e3f4a0d21e6741ac3cc654038d40a8177b7e04625c5fc878390211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 844736d74d8e3349326bf7a9fa1e4fe14a5324d23182cf80c1829c05f60dfcb8 0.600000000000 1696641 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": 1209904, "vin": [ { "gen": { "height": 1209894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "844736d74d8e3349326bf7a9fa1e4fe14a5324d23182cf80c1829c05f60dfcb8" } } ], "extra": [ 1, 82, 169, 72, 15, 233, 254, 151, 227, 244, 160, 210, 30, 103, 65, 172, 60, 198, 84, 3, 141, 64, 168, 23, 123, 126, 4, 98, 92, 95, 200, 120, 57, 2, 17, 0, 0, 0, 3, 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