Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 299c1dae1fd4990c26d887f4d19323244f24f9c55ef9153a8f409ebf37662de7

Tx prefix hash: 16c91dcd95b0b3f541b56bbd4ef8ceb8822b93ea3aac8841a27343b52860bdbf
Tx public key: c4fbab469cfc3897867e8631d6ff252a2e89b39722874275d765b47a07cd2d3f
Timestamp: 1711565400 Timestamp [UCT]: 2024-03-27 18:50:00 Age [y:d:h:m:s]: 01:067:03:09:22
Block: 987647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308973 RingCT/type: yes/0
Extra: 01c4fbab469cfc3897867e8631d6ff252a2e89b39722874275d765b47a07cd2d3f02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5b44c9ede29bf4505ea74ea99aa038815c6115d761ce4f7aaed3012813e2f03 0.600000000000 1447900 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": 987657, "vin": [ { "gen": { "height": 987647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5b44c9ede29bf4505ea74ea99aa038815c6115d761ce4f7aaed3012813e2f03" } } ], "extra": [ 1, 196, 251, 171, 70, 156, 252, 56, 151, 134, 126, 134, 49, 214, 255, 37, 42, 46, 137, 179, 151, 34, 135, 66, 117, 215, 101, 180, 122, 7, 205, 45, 63, 2, 17, 0, 0, 0, 2, 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