Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca01470ad5167c6ec028bbc77ddf97a347d1d7aa8259364032ec59d59016ef74

Tx prefix hash: 2af4ba4018651c23af519e89b112c37936e25cc140247b8d00bc06c3361c4bb3
Tx public key: 2de8f19e25e2b44593a80699d63df828635ccaaaffdcdcbcb68a6b001d4bb4e6
Timestamp: 1718861474 Timestamp [UCT]: 2024-06-20 05:31:14 Age [y:d:h:m:s]: 00:274:00:56:49
Block: 1048117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195829 RingCT/type: yes/0
Extra: 012de8f19e25e2b44593a80699d63df828635ccaaaffdcdcbcb68a6b001d4bb4e602110000000452d47e94000000000000000000

1 output(s) for total of 0.615600000000 dcy

stealth address amount amount idx
00: af3df1abc73a6b055ac0b60b5f851e60cb8c0245adfc9ee1c8435b3dfaf39b73 0.615600000000 1518116 of 0

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": 1048127, "vin": [ { "gen": { "height": 1048117 } } ], "vout": [ { "amount": 615600000, "target": { "key": "af3df1abc73a6b055ac0b60b5f851e60cb8c0245adfc9ee1c8435b3dfaf39b73" } } ], "extra": [ 1, 45, 232, 241, 158, 37, 226, 180, 69, 147, 168, 6, 153, 214, 61, 248, 40, 99, 92, 202, 170, 255, 220, 220, 188, 182, 138, 107, 0, 29, 75, 180, 230, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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