Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acd7d1d3083216a592405a82aa62f67adad259239405eec22251c4c7fb453a8c

Tx prefix hash: 4bd96011d1a89cf9034a624dfc6458817db3d95c3c09fabf81e7497f0a097fa1
Tx public key: 0f545ff5c03c402d0ee759fa73b105989a9d4b6d05931f2e29777363db7a4ac8
Timestamp: 1734447636 Timestamp [UCT]: 2024-12-17 15:00:36 Age [y:d:h:m:s]: 00:107:11:03:58
Block: 1177245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76560 RingCT/type: yes/0
Extra: 010f545ff5c03c402d0ee759fa73b105989a9d4b6d05931f2e29777363db7a4ac80211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f8ed0cfed14fa20dd71187d73e3933cc12bba214fa66a0c4deb85ace617a1a1 0.600000000000 1663610 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": 1177255, "vin": [ { "gen": { "height": 1177245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f8ed0cfed14fa20dd71187d73e3933cc12bba214fa66a0c4deb85ace617a1a1" } } ], "extra": [ 1, 15, 84, 95, 245, 192, 60, 64, 45, 14, 231, 89, 250, 115, 177, 5, 152, 154, 157, 75, 109, 5, 147, 31, 46, 41, 119, 115, 99, 219, 122, 74, 200, 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