Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 184dab12bb67b32717f91cf58a9a1490d0f788c71fab1dbe93bafe1e890e5b80

Tx prefix hash: 8d37c9c62d9047d39ea7023b6bc92bb80d8c8e0230772124d26bf5da857f1f67
Tx public key: 67ae53309298b2eb4bcadb1a859f519dda0d8db1b1133ec3a733e9e79c4bef26
Timestamp: 1736551273 Timestamp [UCT]: 2025-01-10 23:21:13 Age [y:d:h:m:s]: 00:160:01:31:32
Block: 1194626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114090 RingCT/type: yes/0
Extra: 0167ae53309298b2eb4bcadb1a859f519dda0d8db1b1133ec3a733e9e79c4bef26021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7c71788273be91bdda98da38018e8816e8679d09fa26bf76799580a4dfd1251 0.600000000000 1681203 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": 1194636, "vin": [ { "gen": { "height": 1194626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7c71788273be91bdda98da38018e8816e8679d09fa26bf76799580a4dfd1251" } } ], "extra": [ 1, 103, 174, 83, 48, 146, 152, 178, 235, 75, 202, 219, 26, 133, 159, 81, 157, 218, 13, 141, 177, 177, 19, 62, 195, 167, 51, 233, 231, 156, 75, 239, 38, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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