Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac41004e8e1aedcde81a440f9d5c99c42172f25061b43ad63616b8f8976bda73

Tx prefix hash: 4ec9f069d1dde83936c0b9570571aec0080077235846ab22eb4e40b6c1ce9a99
Tx public key: 6f72fb5c07a7009f2dea1ec235a49c56b3323f3ff1657ec4443f6959f2e85a26
Timestamp: 1727462827 Timestamp [UCT]: 2024-09-27 18:47:07 Age [y:d:h:m:s]: 00:117:10:47:18
Block: 1119423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83939 RingCT/type: yes/0
Extra: 016f72fb5c07a7009f2dea1ec235a49c56b3323f3ff1657ec4443f6959f2e85a2602110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbecd51e87ad5742e0d261a5ffde6744354781d16b08c09b13e3ccf3d1191b41 0.600000000000 1600978 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": 1119433, "vin": [ { "gen": { "height": 1119423 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbecd51e87ad5742e0d261a5ffde6744354781d16b08c09b13e3ccf3d1191b41" } } ], "extra": [ 1, 111, 114, 251, 92, 7, 167, 0, 159, 45, 234, 30, 194, 53, 164, 156, 86, 179, 50, 63, 63, 241, 101, 126, 196, 68, 63, 105, 89, 242, 232, 90, 38, 2, 17, 0, 0, 0, 1, 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