Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92db162f9928df572737578d646a603c72b70b284d27fdcbfb3c7f28f62ecf31

Tx prefix hash: c674abc20926888249c988956fc6f05c727a70437763ff3d1b10a733ffe83e78
Tx public key: 25568de7bd8ecc4d02001140021a2025e9e626e40a2bb9787cb8b455f9614aee
Timestamp: 1577177360 Timestamp [UCT]: 2019-12-24 08:49:20 Age [y:d:h:m:s]: 05:044:23:01:50
Block: 30536 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1181964 RingCT/type: yes/0
Extra: 0125568de7bd8ecc4d02001140021a2025e9e626e40a2bb9787cb8b455f9614aee021100000005d81c26c0000000000000000000

1 output(s) for total of 486.208354909000 dcy

stealth address amount amount idx
00: c53b2dff8ceda99f04361b2a7bddb464b4ac2f68883d3ba26710365a96eb2a4a 486.208354909000 50422 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": 30546, "vin": [ { "gen": { "height": 30536 } } ], "vout": [ { "amount": 486208354909, "target": { "key": "c53b2dff8ceda99f04361b2a7bddb464b4ac2f68883d3ba26710365a96eb2a4a" } } ], "extra": [ 1, 37, 86, 141, 231, 189, 142, 204, 77, 2, 0, 17, 64, 2, 26, 32, 37, 233, 230, 38, 228, 10, 43, 185, 120, 124, 184, 180, 85, 249, 97, 74, 238, 2, 17, 0, 0, 0, 5, 216, 28, 38, 192, 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