Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c81c366730572dacad66d52779e92458b9b6cbecd0f738fba4e738ce4944d671

Tx prefix hash: fbaa37a63a199aa80ef9a9d6157d9463c2147465ec53e0e7c3e1b32a7b57310e
Tx public key: c0143fd88d8d072a3af7beb320f7eda33bad69d50d0e2a2c27ad108a1b1d536e
Timestamp: 1728463831 Timestamp [UCT]: 2024-10-09 08:50:31 Age [y:d:h:m:s]: 00:186:01:54:24
Block: 1127716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132798 RingCT/type: yes/0
Extra: 01c0143fd88d8d072a3af7beb320f7eda33bad69d50d0e2a2c27ad108a1b1d536e02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea3a886ed055d5fe46bfa29a9ab569727d146a2affff731c70eb18353d8cdb2f 0.600000000000 1610527 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": 1127726, "vin": [ { "gen": { "height": 1127716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea3a886ed055d5fe46bfa29a9ab569727d146a2affff731c70eb18353d8cdb2f" } } ], "extra": [ 1, 192, 20, 63, 216, 141, 141, 7, 42, 58, 247, 190, 179, 32, 247, 237, 163, 59, 173, 105, 213, 13, 14, 42, 44, 39, 173, 16, 138, 27, 29, 83, 110, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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