Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c946e5cb2f555cd6a979a24cc71154e3b85c1640a8be42c37587286b98801fb

Tx prefix hash: db0b0aa4b9d34fb7f936a5f59325e2d22395ca712e7e37ca7d0fd5394b4f9d52
Tx public key: b88ce6b5cc16c9e7b1ac383c02b1f1a660d195f5e9071d59d86f6541c60e9ae0
Timestamp: 1707813709 Timestamp [UCT]: 2024-02-13 08:41:49 Age [y:d:h:m:s]: 01:052:12:47:25
Block: 956519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298586 RingCT/type: yes/0
Extra: 01b88ce6b5cc16c9e7b1ac383c02b1f1a660d195f5e9071d59d86f6541c60e9ae002110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 653c9b3ac2e0db9ff85423b669ffb96ad8f0dda8d4e24c64b75a918a83851e53 0.600000000000 1415827 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": 956529, "vin": [ { "gen": { "height": 956519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "653c9b3ac2e0db9ff85423b669ffb96ad8f0dda8d4e24c64b75a918a83851e53" } } ], "extra": [ 1, 184, 140, 230, 181, 204, 22, 201, 231, 177, 172, 56, 60, 2, 177, 241, 166, 96, 209, 149, 245, 233, 7, 29, 89, 216, 111, 101, 65, 198, 14, 154, 224, 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