Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ffae1a86e3bcc7edfb774806c9514af545d14466a5f55014e6ea6f2672f1d92

Tx prefix hash: be164d859ec3f6282bec94d578dea70c051b81e5c55d55d71427ec067c908fb0
Tx public key: 75e46413c03ef147f2c6712f7c9db0d8e363a028cdc2e2f39ee71ab6b61144e8
Timestamp: 1701642362 Timestamp [UCT]: 2023-12-03 22:26:02 Age [y:d:h:m:s]: 01:045:09:37:01
Block: 905357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293825 RingCT/type: yes/0
Extra: 0175e46413c03ef147f2c6712f7c9db0d8e363a028cdc2e2f39ee71ab6b61144e8021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.614011356000 dcy

stealth address amount amount idx
00: 2f46a5e97ea458d48f2be96fb8e7bf72e1753d03fef00e640ecc4e618d8c2d48 0.614011356000 1362240 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": 905367, "vin": [ { "gen": { "height": 905357 } } ], "vout": [ { "amount": 614011356, "target": { "key": "2f46a5e97ea458d48f2be96fb8e7bf72e1753d03fef00e640ecc4e618d8c2d48" } } ], "extra": [ 1, 117, 228, 100, 19, 192, 62, 241, 71, 242, 198, 113, 47, 124, 157, 176, 216, 227, 99, 160, 40, 205, 194, 226, 243, 158, 231, 26, 182, 182, 17, 68, 232, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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