Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 927ad2065e3ee0f22e5c0ec1492d86a32f3c5041dee5938ddae1022913a65a23

Tx prefix hash: 42606b20983b5d68d30d7f443375f3b244722106b1c4b5bbc2d7bc8c64229acc
Tx public key: 160b63b4d1706e725eac937690a5fce9fd7910fdcecb795a414a07d7397b8fbd
Timestamp: 1706667581 Timestamp [UCT]: 2024-01-31 02:19:41 Age [y:d:h:m:s]: 01:294:21:02:31
Block: 947005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469551 RingCT/type: yes/0
Extra: 01160b63b4d1706e725eac937690a5fce9fd7910fdcecb795a414a07d7397b8fbd02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4c708f1cd377f825179565ba9bf3ff196992e3e0cb5f03499256d3614065af4 0.600000000000 1405351 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": 947015, "vin": [ { "gen": { "height": 947005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4c708f1cd377f825179565ba9bf3ff196992e3e0cb5f03499256d3614065af4" } } ], "extra": [ 1, 22, 11, 99, 180, 209, 112, 110, 114, 94, 172, 147, 118, 144, 165, 252, 233, 253, 121, 16, 253, 206, 203, 121, 90, 65, 74, 7, 215, 57, 123, 143, 189, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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