Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 315c7c41dc4e566afe223808395e9bcad5241d07a08b7d6095d1c2406f7444a6

Tx prefix hash: a9280c84a692791386eb7b0b2c1816ef7cc7b3b12276abd15f663fe03c00d930
Tx public key: 9748f2d3ff89089f0d1bcb55d7637ff58679f6b4e24c632022a3af4095711f64
Timestamp: 1704737635 Timestamp [UCT]: 2024-01-08 18:13:55 Age [y:d:h:m:s]: 01:141:03:57:49
Block: 931012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362035 RingCT/type: yes/0
Extra: 019748f2d3ff89089f0d1bcb55d7637ff58679f6b4e24c632022a3af4095711f640211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b432ccb10292d918b03ba72230ede4ff5961fa5fd0f9e45bbfe06d0e360a43f6 0.600000000000 1388904 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": 931022, "vin": [ { "gen": { "height": 931012 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b432ccb10292d918b03ba72230ede4ff5961fa5fd0f9e45bbfe06d0e360a43f6" } } ], "extra": [ 1, 151, 72, 242, 211, 255, 137, 8, 159, 13, 27, 203, 85, 215, 99, 127, 245, 134, 121, 246, 180, 226, 76, 99, 32, 34, 163, 175, 64, 149, 113, 31, 100, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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