Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45a2e9353e6db0c8c1947ab8041d8f527db7065c28ccbb76b592ddfb8a16236f

Tx prefix hash: 8d9482a0682544423f6797a8a9e95fc8389eba300db16df44c9152e63fc8f9ff
Tx public key: a7aa7a41eb3492426b4e36100fb56cf595942f02940113a35b1ad28faf5a1243
Timestamp: 1709456114 Timestamp [UCT]: 2024-03-03 08:55:14 Age [y:d:h:m:s]: 01:220:05:25:24
Block: 970145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416070 RingCT/type: yes/0
Extra: 01a7aa7a41eb3492426b4e36100fb56cf595942f02940113a35b1ad28faf5a12430211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fb8366c6624cdea394d1dee88fca7d7b0fe65ccf820561bfdd2712cd1df3fd5 0.600000000000 1429994 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": 970155, "vin": [ { "gen": { "height": 970145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fb8366c6624cdea394d1dee88fca7d7b0fe65ccf820561bfdd2712cd1df3fd5" } } ], "extra": [ 1, 167, 170, 122, 65, 235, 52, 146, 66, 107, 78, 54, 16, 15, 181, 108, 245, 149, 148, 47, 2, 148, 1, 19, 163, 91, 26, 210, 143, 175, 90, 18, 67, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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