Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 097f991f316032b1c1c31c178865ad476bba0b0c5ff59a4ea8c39e073583f171

Tx prefix hash: beff01fe14924e0ab81da968068837f87f27aa7b5f74740cc127173de8b7f113
Tx public key: 001d2c39b1594988151a23d52b58e8aff1bd61216a99c2813f8339d55c15f4fd
Timestamp: 1726600415 Timestamp [UCT]: 2024-09-17 19:13:35 Age [y:d:h:m:s]: 00:207:03:39:49
Block: 1112271 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147877 RingCT/type: yes/0
Extra: 01001d2c39b1594988151a23d52b58e8aff1bd61216a99c2813f8339d55c15f4fd02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62d74b15a4cc2fa0c9c1a2ba0c0c18a32d99449fdc9ea5cddbd71bea34e7fbe9 0.600000000000 1591534 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": 1112281, "vin": [ { "gen": { "height": 1112271 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62d74b15a4cc2fa0c9c1a2ba0c0c18a32d99449fdc9ea5cddbd71bea34e7fbe9" } } ], "extra": [ 1, 0, 29, 44, 57, 177, 89, 73, 136, 21, 26, 35, 213, 43, 88, 232, 175, 241, 189, 97, 33, 106, 153, 194, 129, 63, 131, 57, 213, 92, 21, 244, 253, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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