Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f74f0ee672a55e0c78b1cc5fa86e70ccf30a821106e2d5b23660388abad4684b

Tx prefix hash: 5560fe37c1ee3d72ac31c95f77bbfa8b8314584bd6c1d541301f3a71d294fbe2
Tx public key: 8197ff43566385a5c0f1c509d46dd91f7129ed0c67c9843fb6ce38646f6728c8
Timestamp: 1725586830 Timestamp [UCT]: 2024-09-06 01:40:30 Age [y:d:h:m:s]: 00:204:12:47:58
Block: 1103880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146011 RingCT/type: yes/0
Extra: 018197ff43566385a5c0f1c509d46dd91f7129ed0c67c9843fb6ce38646f6728c8021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 246db8c698b43a1d45d8b2ca7a9235b09342b8860c0a7689405f44b0ff2a5f77 0.600000000000 1580877 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": 1103890, "vin": [ { "gen": { "height": 1103880 } } ], "vout": [ { "amount": 600000000, "target": { "key": "246db8c698b43a1d45d8b2ca7a9235b09342b8860c0a7689405f44b0ff2a5f77" } } ], "extra": [ 1, 129, 151, 255, 67, 86, 99, 133, 165, 192, 241, 197, 9, 212, 109, 217, 31, 113, 41, 237, 12, 103, 201, 132, 63, 182, 206, 56, 100, 111, 103, 40, 200, 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