Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e48dd86f9596f177c93a32e2ed7736b42ee3fee00714f74954b1055a01f58d4f

Tx prefix hash: 466ecfafb5eadad26dc085d389547956abf648b70fd170435a0a87b1df333fbb
Tx public key: 4f9bfea0ce2281dc86bb2f7590548b4474e8b0a3b8de67fae729e000ab8aa472
Timestamp: 1705457825 Timestamp [UCT]: 2024-01-17 02:17:05 Age [y:d:h:m:s]: 01:099:07:24:30
Block: 936964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332103 RingCT/type: yes/0
Extra: 014f9bfea0ce2281dc86bb2f7590548b4474e8b0a3b8de67fae729e000ab8aa47202110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf4cc1e1fbc791ae2b783c2cc2bd1072995873d97d9e87addd640525ec8bb667 0.600000000000 1395008 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": 936974, "vin": [ { "gen": { "height": 936964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf4cc1e1fbc791ae2b783c2cc2bd1072995873d97d9e87addd640525ec8bb667" } } ], "extra": [ 1, 79, 155, 254, 160, 206, 34, 129, 220, 134, 187, 47, 117, 144, 84, 139, 68, 116, 232, 176, 163, 184, 222, 103, 250, 231, 41, 224, 0, 171, 138, 164, 114, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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