Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 492b80f4d1407fd43d46720d2f031d4c90daeac2365fd2c599a80c74dec4b240

Tx prefix hash: 6bbd5c0ef64244c4d2c6eb09d0587df3e00ac8140839c801b31d62f1f654faab
Tx public key: 1fd50a44ffc3eb6d594662aee4bdfd3c3791d8c613a84af5647b73ecfb9373a3
Timestamp: 1578441082 Timestamp [UCT]: 2020-01-07 23:51:22 Age [y:d:h:m:s]: 05:092:10:18:33
Block: 40864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1216040 RingCT/type: yes/0
Extra: 011fd50a44ffc3eb6d594662aee4bdfd3c3791d8c613a84af5647b73ecfb9373a302110000002e49b77a3d000000000000000000

1 output(s) for total of 449.377024322000 dcy

stealth address amount amount idx
00: 8fedfa41141772a3fcdfec0eb0ec92326cb25de03e7e9a73b4486ee1803f0a47 449.377024322000 72217 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": 40874, "vin": [ { "gen": { "height": 40864 } } ], "vout": [ { "amount": 449377024322, "target": { "key": "8fedfa41141772a3fcdfec0eb0ec92326cb25de03e7e9a73b4486ee1803f0a47" } } ], "extra": [ 1, 31, 213, 10, 68, 255, 195, 235, 109, 89, 70, 98, 174, 228, 189, 253, 60, 55, 145, 216, 198, 19, 168, 74, 245, 100, 123, 115, 236, 251, 147, 115, 163, 2, 17, 0, 0, 0, 46, 73, 183, 122, 61, 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