Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47c861cfa3eb01a1528b5a1611af8b72dfe630bb523f304e40dc924b558686b0

Tx prefix hash: a51477d0f93d11146234898d6b595aca00b12118c9b7f5d8f4f75460fdc01571
Tx public key: 5ccea3ff1a2f3b813f9375235981a665daa60d7c35f54d89d5133a4aa0d1bcd2
Timestamp: 1702671248 Timestamp [UCT]: 2023-12-15 20:14:08 Age [y:d:h:m:s]: 01:036:12:06:16
Block: 913891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287395 RingCT/type: yes/0
Extra: 015ccea3ff1a2f3b813f9375235981a665daa60d7c35f54d89d5133a4aa0d1bcd202110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59156eee09c72bb968f60a030937b0eb28861233a5ba8a489fe94ed700d83996 0.600000000000 1371171 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": 913901, "vin": [ { "gen": { "height": 913891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59156eee09c72bb968f60a030937b0eb28861233a5ba8a489fe94ed700d83996" } } ], "extra": [ 1, 92, 206, 163, 255, 26, 47, 59, 129, 63, 147, 117, 35, 89, 129, 166, 101, 218, 166, 13, 124, 53, 245, 77, 137, 213, 19, 58, 74, 160, 209, 188, 210, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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