Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 461a3a4687233561c10bb1487658b00033cfe3a40930a1f57da71f6c4d06e0e3

Tx prefix hash: 42d12f25204c417ab33110ccc4d0ad3ed9fa1e079b5417bef6261c95dd93fdec
Tx public key: 273b36c98e12d40d5806b02c7d33dc50086b17b0f0925012e89fa4d5e212f660
Timestamp: 1628894259 Timestamp [UCT]: 2021-08-13 22:37:39 Age [y:d:h:m:s]: 03:274:04:03:36
Block: 313469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 968974 RingCT/type: yes/0
Extra: 01273b36c98e12d40d5806b02c7d33dc50086b17b0f0925012e89fa4d5e212f66002110000001ae6f80b5a000000000000000000

1 output(s) for total of 56.150373751000 dcy

stealth address amount amount idx
00: 1c4ec4308c6d9db2fc45bc71e1d9c3a5c8cb1a3ce0e8a76423e23a2a6a0dd955 56.150373751000 652380 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": 313479, "vin": [ { "gen": { "height": 313469 } } ], "vout": [ { "amount": 56150373751, "target": { "key": "1c4ec4308c6d9db2fc45bc71e1d9c3a5c8cb1a3ce0e8a76423e23a2a6a0dd955" } } ], "extra": [ 1, 39, 59, 54, 201, 142, 18, 212, 13, 88, 6, 176, 44, 125, 51, 220, 80, 8, 107, 23, 176, 240, 146, 80, 18, 232, 159, 164, 213, 226, 18, 246, 96, 2, 17, 0, 0, 0, 26, 230, 248, 11, 90, 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