Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 140c05244d42bf81128382fbf4dcff87cde476968316ce6e282362f716537fc9

Tx prefix hash: 6c68be12535021cea469adf59bd8204ee26711f8ae9ebacd51d3b746b268d53b
Tx public key: 32059ce9a1d2b0ef1db31f190174f14dfa8c98d51a80e6f5b321f22e929b08fd
Timestamp: 1702034057 Timestamp [UCT]: 2023-12-08 11:14:17 Age [y:d:h:m:s]: 01:101:23:30:10
Block: 908599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334051 RingCT/type: yes/0
Extra: 0132059ce9a1d2b0ef1db31f190174f14dfa8c98d51a80e6f5b321f22e929b08fd02110000000333af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95e08f03dc5ab54d1363bf2af372b8e60112e3e2a03df6a3d2318741a02882be 0.600000000000 1365644 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": 908609, "vin": [ { "gen": { "height": 908599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95e08f03dc5ab54d1363bf2af372b8e60112e3e2a03df6a3d2318741a02882be" } } ], "extra": [ 1, 50, 5, 156, 233, 161, 210, 176, 239, 29, 179, 31, 25, 1, 116, 241, 77, 250, 140, 152, 213, 26, 128, 230, 245, 179, 33, 242, 46, 146, 155, 8, 253, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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